Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. A user cannot call a number that matches a normalization rule that begins with optional digits in a Lync Server 2010 environment

A user cannot call a number that matches a normalization rule that begins with optional digits in a Lync Server 2010 environment

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You deploy Enterprise Voice in a Microsoft Lync Server 2010 environment.
  • You create a telephone number normalization rule. The pattern of this rule includes a prefix that contains optional digits, such as a question mark (?) or an asterisk (*). For example, you set the Pattern to match field to ^(1)?([2-9]\d\d[2-9]\d{6})$ and the Translation rule field to +1$2. This rule changes the telephone numbers 1XXXXXXXXXX and XXXXXXXXXX to +1XXXXXXXXXX.
  • A user in the environment makes a call to a telephone number by using a client that does not support client-side normalization. For example, the user uses the Unified Messaging Play on Phone feature in Microsoft Exchange or a Public Switched Telephone Network (PSTN) telephone.
  • The telephone number matches the pattern but does not contain the prefix. For example, the user dials XXXXXXXXXX.
In this scenario, the user cannot make the call.

↑ Back to the top

Cause

This issue occurs because the prefix matching optimization that Lync Server 2010 uses to change telephone numbers cannot handle expressions that begin with optional digits.

↑ Back to the top

Resolution

To resolve this issue, install the following cumulative update:
2670352 Description of the cumulative update for Lync Server 2010: February 2012

↑ Back to the top

Workaround

To work around the issue, use two rules instead of one. One rule should contain the prefix, and the other rule should not contain the prefix. 

For example, you can use the following two rules instead of the rule that is described in the "Symptoms" section:
  • In the first rule, set the Pattern to match field to ^1([2-9]\d\d[2-9]\d{6})$ and set the Translation rule field to +1$1.
  • In the second rule, set the Pattern to match field to ^([2-9]\d\d[2-9]\d{6})$ and set the Translation rule field to +1$1.

↑ Back to the top

More Information

For more information about the telephone normalization rules, visit the following Microsoft website:
General information about the telephone normalization rules
For more information about the telephone number normalization rule regular expressions, visit the following Microsoft website:
General information about the telephone number normalization rule regular expressions
For more information about how to define translation rules, visit the following Microsoft website:
How to define translation rules
For more information about how to create or modify a translation rule manually, visit the following Microsoft website:
How to create or modify a translation rule manually

↑ Back to the top

Keywords: kbqfe, kbfix, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2673302
Revision : 1
Created on : 1/7/2017
Published on : 3/1/2012
Exists online : False
Views : 343